Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1370

reference: 255-tree-1
name: 1370
tree-preservation-order: undefined
255-tpo-1
uprn
address-text
point: POINT (-0.991332 50.874960)
geometry: MULTIPOLYGON (((-0.991233 50.874950,-0.991237 50.874969,-0.991251 50.874987,-0.991273 50.875001,-0.991300 50.875010,-0.991331 50.875014,-0.991362 50.875011,-0.991390 50.875002,-0.991412 50.874988,-0.991426 50.874971,-0.991432 50.874952,-0.991427 50.874932,-0.991414 50.874914,-0.991392 50.874900,-0.991364 50.874891,-0.991334 50.874888,-0.991303 50.874891,-0.991275 50.874899,-0.991253 50.874913,-0.991238 50.874930,-0.991233 50.874950)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL